Dark fiber dense wavelength division multiplexing service path design for microservices for 5g or other next generation network

ABSTRACT

A dark fiber dense wavelength division multiplexing service path design microservice (ddSPDmS) can provide a scalable self-contained meta-data driven approach for a flexible implementation of a dark fiber dense wavelength division multiplexing (DWDM) service path design solution. The service plan design solution can be used as a standalone solution or integrated with a network management application. In order to manage a large volume of circuit designs, multiple microservices can accept application program interface (API) requests in a cloud environment. Permission can then be given to any application to use the API to make a call to the design and inventory. Additionally, metadata templates can be designed to support a node, a link, and/or a topology for the microservices.

RELATED APPLICATIONS

The subject patent application is a continuation of, and claims priorityto each of, U.S. patent application Ser. No. 17/319,067, filed May 12,2021, and entitled “DARK FIBER DENSE WAVELENGTH DIVISION MULTIPLEXINGSERVICE PATH DESIGN FOR MICROSERVICES FOR 5G OR OTHER NEXT GENERATIONNETWORK,” which is a continuation of U.S. patent application Ser. No.16/212,972 (now U.S. Pat. No. 11,025,340), filed Dec. 7, 2018, andentitled “DARK FIBER DENSE WAVELENGTH DIVISION MULTIPLEXING SERVICE PATHDESIGN FOR MICROSERVICES FOR 5G OR OTHER NEXT GENERATION NETWORK,” theentireties of which priority applications are hereby incorporated byreference herein.

TECHNICAL FIELD

This disclosure relates generally to facilitating dark fiber wavelengthdivision multiplexing. For example, this disclosure relates tofacilitating dark fiber wavelength division multiplexing service pathdesign for microservices for a 5G, or other next generation network, airinterface.

BACKGROUND

5^(th) generation (5G) wireless systems represent a next major phase ofmobile telecommunications standards beyond the currenttelecommunications standards of 4^(th) generation (4G). Rather thanfaster peak Internet connection speeds, 5G planning aims at highercapacity than current 4G, allowing a higher number of mobile broadbandusers per area unit, and allowing consumption of higher or unlimiteddata quantities. This would enable a large portion of the population tostream high-definition media many hours per day with their mobiledevices, when out of reach of wireless fidelity hotspots. 5G researchand development also aims at improved support of machine-to-machinecommunication, also known as the Internet of things, aiming at lowercost, lower battery consumption, and lower latency than 4G equipment.

Microservices are an example of a software architectural style in whichlarge applications are composed from small loosely coupled services withindependent lifecycles. Microservice architecture evolved from themanaging of complex monolithic style applications that are built as asingle unit. The entire application is packaged into a single webapplication archive (WAR) or enterprise application archive (EAR). Asthe application grows and becomes more complex, complications arise. Achange to one part of the application may require that the entireapplication be rebuilt, retested, packaged, and deployed. Anotherconcern is that parts of the application may scale differently thanothers, thus prompting the entire application to be scaled in effectaccording to a lowest common denominator.

The above-described background relating to a service path design formicroservices is merely intended to provide a contextual overview ofsome current issues, and is not intended to be exhaustive. Othercontextual information may become further apparent upon review of thefollowing detailed description.

BRIEF DESCRIPTION OF THE DRAWINGS

Non-limiting and non-exhaustive embodiments of the subject disclosureare described with reference to the following figures, wherein likereference numerals refer to like parts throughout the various viewsunless otherwise specified.

FIG. 1 illustrates an example wireless communication system in which anetwork node device (e.g., network node) and user equipment (UE) canimplement various aspects and embodiments of the subject disclosure.

FIG. 2 illustrates an example schematic system block diagram of aservice path design according to one or more embodiments.

FIG. 3 illustrates an example schematic system block diagram ofpoint-to-point service path according to one or more embodiments.

FIG. 4 illustrates an example schematic system block diagram of a hubservice path according to one or more embodiments.

FIG. 5 illustrates an example schematic system block diagram of a ringservice path according to one or more embodiments.

FIG. 6 illustrates an example schematic system block diagram of combinedservice paths according to one or more embodiments.

FIG. 7 illustrates an example schematic system block diagram of a ringrouting option according to one or more embodiments.

FIG. 8 illustrates an example flow diagram for a method for a servicepath design network according to one or more embodiments.

FIG. 9 illustrates an example flow diagram for a system for a servicepath design network according to one or more embodiments.

FIG. 10 illustrates an example flow diagram for a machine-readablemedium for a service path design network according to one or moreembodiments.

FIG. 11 illustrates an example block diagram of an example mobilehandset operable to engage in a system architecture that facilitatessecure wireless communication according to one or more embodimentsdescribed herein.

FIG. 12 illustrates an example block diagram of an example computeroperable to engage in a system architecture that facilitates securewireless communication according to one or more embodiments describedherein.

DETAILED DESCRIPTION

In the following description, numerous specific details are set forth toprovide a thorough understanding of various embodiments. One skilled inthe relevant art will recognize, however, that the techniques describedherein can be practiced without one or more of the specific details, orwith other methods, components, materials, etc. In other instances,well-known structures, materials, or operations are not shown ordescribed in detail to avoid obscuring certain aspects.

Reference throughout this specification to “one embodiment,” or “anembodiment,” means that a particular feature, structure, orcharacteristic described in connection with the embodiment is includedin at least one embodiment. Thus, the appearances of the phrase “in oneembodiment,” “in one aspect,” or “in an embodiment,” in various placesthroughout this specification are not necessarily all referring to thesame embodiment. Furthermore, the particular features, structures, orcharacteristics may be combined in any suitable manner in one or moreembodiments.

As utilized herein, terms “component,” “system,” “interface,” and thelike are intended to refer to a computer-related entity, hardware,software (e.g., in execution), and/or firmware. For example, a componentcan be a processor, a process running on a processor, an object, anexecutable, a program, a storage device, and/or a computer. By way ofillustration, an application running on a server and the server can be acomponent. One or more components can reside within a process, and acomponent can be localized on one computer and/or distributed betweentwo or more computers.

Further, these components can execute from various machine-readablemedia having various data structures stored thereon. The components cancommunicate via local and/or remote processes such as in accordance witha signal having one or more data packets (e.g., data from one componentinteracting with another component in a local system, distributedsystem, and/or across a network, e.g., the Internet, a local areanetwork, a wide area network, etc. with other systems via the signal).

As another example, a component can be an apparatus with specificfunctionality provided by mechanical parts operated by electric orelectronic circuitry; the electric or electronic circuitry can beoperated by a software application or a firmware application executed byone or more processors; the one or more processors can be internal orexternal to the apparatus and can execute at least a part of thesoftware or firmware application. As yet another example, a componentcan be an apparatus that provides specific functionality throughelectronic components without mechanical parts; the electroniccomponents can include one or more processors therein to executesoftware and/or firmware that confer(s), at least in part, thefunctionality of the electronic components. In an aspect, a componentcan emulate an electronic component via a virtual machine, e.g., withina cloud computing system.

The words “exemplary” and/or “demonstrative” are used herein to meanserving as an example, instance, or illustration. For the avoidance ofdoubt, the subject matter disclosed herein is not limited by suchexamples. In addition, any aspect or design described herein as“exemplary” and/or “demonstrative” is not necessarily to be construed aspreferred or advantageous over other aspects or designs, nor is it meantto preclude equivalent exemplary structures and techniques known tothose of ordinary skill in the art. Furthermore, to the extent that theterms “includes,” “has,” “contains,” and other similar words are used ineither the detailed description or the claims, such terms are intendedto be inclusive—in a manner similar to the term “comprising” as an opentransition word—without precluding any additional or other elements.

As used herein, the term “infer” or “inference” refers generally to theprocess of reasoning about, or inferring states of, the system,environment, user, and/or intent from a set of observations as capturedvia events and/or data. Captured data and events can include user data,device data, environment data, data from sensors, sensor data,application data, implicit data, explicit data, etc. Inference can beemployed to identify a specific context or action, or can generate aprobability distribution over states of interest based on aconsideration of data and events, for example.

Inference can also refer to techniques employed for composinghigher-level events from a set of events and/or data. Such inferenceresults in the construction of new events or actions from a set ofobserved events and/or stored event data, whether the events arecorrelated in close temporal proximity, and whether the events and datacome from one or several event and data sources. Various classificationschemes and/or systems (e.g., support vector machines, neural networks,expert systems, Bayesian belief networks, fuzzy logic, and data fusionengines) can be employed in connection with performing automatic and/orinferred action in connection with the disclosed subject matter.

In addition, the disclosed subject matter can be implemented as amethod, apparatus, or article of manufacture using standard programmingand/or engineering techniques to produce software, firmware, hardware,or any combination thereof to control a computer to implement thedisclosed subject matter. The term “article of manufacture” as usedherein is intended to encompass a computer program accessible from anycomputer-readable device, machine-readable device, computer-readablecarrier, computer-readable media, or machine-readable media. Forexample, computer-readable media can include, but are not limited to, amagnetic storage device, e.g., hard disk; floppy disk; magneticstrip(s); an optical disk (e.g., compact disk (CD), a digital video disc(DVD), a Blu-ray Disc™ (BD)); a smart card; a flash memory device (e.g.,card, stick, key drive); and/or a virtual device that emulates a storagedevice and/or any of the above computer-readable media.

As an overview, various embodiments are described herein to facilitatedark fiber wavelength division multiplexing service path design formicroservices for a 5G air interface or other next generation networks.For simplicity of explanation, the methods (or algorithms) are depictedand described as a series of acts. It is to be understood andappreciated that the various embodiments are not limited by the actsillustrated and/or by the order of acts. For example, acts can occur invarious orders and/or concurrently, and with other acts not presented ordescribed herein. Furthermore, not all illustrated acts may be requiredto implement the methods. In addition, the methods could alternativelybe represented as a series of interrelated states via a state diagram orevents. Additionally, the methods described hereafter are capable ofbeing stored on an article of manufacture (e.g., a machine-readablestorage medium) to facilitate transporting and transferring suchmethodologies to computers. The term article of manufacture, as usedherein, is intended to encompass a computer program accessible from anycomputer-readable device, carrier, or media, including a non-transitorymachine-readable storage medium.

It should be noted that although various aspects and embodiments havebeen described herein in the context of 5G, Universal MobileTelecommunications System (UMTS), and/or Long Term Evolution (LTE), orother next generation networks, the disclosed aspects are not limited to5G, a UMTS implementation, and/or an LTE implementation as thetechniques can also be applied in 3G, 4G or LTE systems. For example,aspects or features of the disclosed embodiments can be exploited insubstantially any wireless communication technology. Such wirelesscommunication technologies can include UMTS, Code Division MultipleAccess (CDMA), Wi-Fi, Worldwide Interoperability for Microwave Access(WiMAX), General Packet Radio Service (GPRS), Enhanced GPRS, ThirdGeneration Partnership Project (3GPP), LTE, Third Generation PartnershipProject 2 (3GPP2) Ultra Mobile Broadband (UMB), High Speed Packet Access(HSPA), Evolved High Speed Packet Access (HSPA+), High-Speed DownlinkPacket Access (HSDPA), High-Speed Uplink Packet Access (HSUPA), Zigbee,or another IEEE 802.XX technology. Additionally, substantially allaspects disclosed herein can be exploited in legacy telecommunicationtechnologies.

Described herein are systems, methods, articles of manufacture, andother embodiments or implementations that can facilitate dark fiberwavelength division multiplexing service path design for microservicesfor a 5G network. Facilitating a dark fiber wavelength divisionmultiplexing service path design for microservices for a 5G network canbe implemented in connection with any type of device with a connectionto the communications network (e.g., a mobile handset, a computer, ahandheld device, etc.) any Internet of things (IOT) device (e.g.,toaster, coffee maker, blinds, music players, speakers, etc.), and/orany connected vehicles (cars, airplanes, space rockets, and/or other atleast partially automated vehicles (e.g., drones)). In some embodimentsthe non-limiting term user equipment (UE) is used. It can refer to anytype of wireless device that communicates with a radio network node in acellular or mobile communication system. Examples of UE are targetdevice, device to device (D2D) UE, machine type UE or UE capable ofmachine to machine (M2M) communication, PDA, Tablet, mobile terminals,smart phone, laptop embedded equipped (LEE), laptop mounted equipment(LME), USB dongles, etc. Note that the terms element, elements andantenna ports can be interchangeably used but carry the same meaning inthis disclosure. The embodiments are applicable to single carrier aswell as to multicarrier (MC) or carrier aggregation (CA) operation ofthe UE. The term carrier aggregation (CA) is also called (e.g.,interchangeably called) “multi-carrier system”, “multi-cell operation”,“multi-carrier operation”, “multi-carrier” transmission and/orreception.

In some embodiments the non-limiting term radio network node or simplynetwork node is used. It can refer to any type of network node thatserves UE is connected to other network nodes or network elements or anyradio node from where UE receives a signal. Examples of radio networknodes are Node B, base station (BS), multi-standard radio (MSR) nodesuch as MSR BS, eNode B, network controller, radio network controller(RNC), base station controller (BSC), relay, donor node controllingrelay, base transceiver station (BTS), access point (AP), transmissionpoints, transmission nodes, RRU, RRH, nodes in distributed antennasystem (DAS), etc.

Cloud radio access networks (RAN) can enable the implementation ofconcepts such as software-defined network (SDN) and network functionvirtualization (NFV) in 5G networks. This disclosure can facilitate ageneric channel state information framework design for a 5G network.Certain embodiments of this disclosure can comprise an SDN controllerthat can control routing of traffic within the network and between thenetwork and traffic destinations. The SDN controller can be merged withthe 5G network architecture to enable service deliveries via openapplication programming interfaces (“APIs”) and move the network coretowards an all internet protocol (“IP”), cloud based, and softwaredriven telecommunications network. The SDN controller can work with, ortake the place of policy and charging rules function (“PCRF”) networkelements so that policies such as quality of service and trafficmanagement and routing can be synchronized and managed end to end.

To meet the huge demand for data centric applications, 4G standards canbe applied 5G, also called new radio (NR) access. 5G networks cancomprise the following: data rates of several tens of megabits persecond supported for tens of thousands of users; 1 gigabit per secondcan be offered simultaneously to tens of workers on the same officefloor; several hundreds of thousands of simultaneous connections can besupported for massive sensor deployments; spectral efficiency can beenhanced compared to 4G; improved coverage; enhanced signalingefficiency; and reduced latency compared to LTE. In multicarrier systemsuch as OFDM, each subcarrier can occupy bandwidth (e.g., subcarrierspacing). If the carriers use the same bandwidth spacing, then it can beconsidered a single numerology. However, if the carriers occupydifferent bandwidth and/or spacing, then it can be considered a multiplenumerology.

The microservice architectural style composes applications fromseparate, independent services that provide a single domain capability.This allows parts of the application to be changed and evolve over timewithout impacting other parts of the application. Microservices aredesigned to be independently developed, tested, deployed, configured,upgraded, scaled, monitored, and administered. In particular,independent deployment is a fundamental capability. Microservices can bestandalone executable processes that cannot be deployed withinapplication servers alongside other services. Microservices can hideimplementation details, thus insulating microservice consumers fromchanges within or downstream from the services they consume.

As part of encapsulation, microservices can keep persistent data privateto the service and accessible only via its application program interface(API). Thus, microservices cannot integrate at the data layer nor sharethe same database or database schema with other services. Additionally,automation of microservices can apply to all aspects of a microservices.Automation embraces development operations, continuous integration, anddelivery processes including, but not limited to: automated testing,automated deployment, automated scaling, zero-touch rolling upgradesand/or downgrades, etc.

A dark fiber dense wavelength division multiplexing service path designmicroservice (ddSPDmS) can provide a scalable self-contained meta-datadriven approach for a flexible implementation of a dark fiber densewavelength division multiplexing (DWDM) service path design solution.The design solution can be used as a standalone solution or integratedwith a network management application. In order to put light on a darkfiber, the dark fiber can be connected to network equipment based on alayer. The fiber can be connected to a service switching port (SSP) toget the light to transmit the signal over a channel. The signal can bemultiplexed (Mux) on one side and then demultiplexed (deMux) on theother side to get the needed signal. In order to manage a large volumeof circuit design and build the circuit design into an inventorydatabase, multiple microservices can accept application programinterface (API) requests exposed by the microservice in a cloudenvironment. Permission can then be given to any application to use theAPI to make a call to the design and inventory database to use themicroservice at a later time. A metadata template can be designed tosupport a node, a link, and/or a topology for a service.

Increased MIMO for LTE advanced (LTE-A) and 5G massive MIMO design canrequire a higher transport link capacity in addition to a low latencytransport that can have less transport overhead. Ethernet to a cell sitemay not be an economical choice for the high-speed links. In somescenarios such as with remote cell sites, Ethernet to a cell site maynot meet the 5G low latency use cases. Centralized radio access network(cRAN) deployment in hub offices with remote baseband unit (BBU) poolingand remote radio head (RRH— network densification) can require fibertransport with channelization (dense wavelength division multiplexing(DWDM)—reduce the fiber costs) for backhaul, shorthaul and/or fronthaul.To meet the demand of higher capacity links with low cost, mobileoperators can utilize dark fiber powered by DWDM devices to connect andaggregate radio access network (RAN) traffic into a mobile transportswitching office. Automated design of service path with various topologyof dark fiber and DWDM devices can utilize a cloud-based,self-contained, and meta-data driven approach for a low cost and fasttime to market solutions.

The ddSPD micro service can provide various templates to support thedata model such as: a node template, a link template, and/or a ruletemplate. The ddSPD micro service can also automate the design servicepath topologies such as: ring, point-to-point and hub-spoke.Additionally, the ddSPD micro service can also provide representationalstate transfer (REST) application program interfaces (API) with standardmeta-data such as javascript object notation (JSON) for integrationflexibility to support new use cases. RESTful (JSON) APIs can supportthe service path APIs for various components and system integration persupported use case in the topology templates. A device template candefine nodes per topology and device components such as: slots, chassis,cards, ports, small form-factor pluggable transceiver (SFPs),multiplexers, demultiplexers, transponders, etc. The aforementioneddevice components can be cached from an inventory data model. A rulestemplate can define business rules on the connectivity of the links,cables, device service modules such as jumpers, and fiber for a servicepath topology. Additionally, a link template can define physical and/orlogical connection end points per topology template.

The topology template can define the topology use cases that themicroservice can support for the service path, such as: point-to-point,hub-spoke, ring, etc. It can also define a micro flow to create thedesign. Additionally, the topology template can support multi-linksegments such as a wavelength path within a service path. The micro flowcan provide sequencing for the topology template to design the servicepath. This can be a cross-platform javascript run-time environment(NodeJS) sequencing or other comparable technology for micro flowsequencing. Additionally, database management systems (DBMS) (e.g.,MariaDB) can be leveraged for the micro service to store the meta-data,logic, and service path design for the macro orchestration flow lifecycle or optionally as a service path in a stand-alone deployment.Furthermore, an inventory (INV) API/DBMS driver can provide API or DBMSdriver functions to cache the device data, service path from theinventory, and/or update the design into inventory. A graphical userinterface (GUI) (e.g., internal or external) can display the designedservice path and templates to a user to provide the user with editcapabilities. The GUI can use the same RESTful API provided by themicroservice. For example, a standard web browser can be used with JSONto display API responses. Thus, micro service solutions can provide acloud-based, self-contained code that provides easy instantiations forscale and ease of integration with a network management applicationorchestration and inventory database. It should be noted that this microservice meta-data driven solution is not limited to automation of DWDMservice path. Other mobile backhaul solution use cases, such as switchedEthernet and dedicated Ethernet, can also be included.

In one embodiment, described herein is a method comprising receiving, bya wireless network device comprising a processor, first orchestrationflow data representative of a first service flow of a service of awireless network. The method can also comprise applying, by the wirelessnetwork device, topology template data, representative of a topology, tothe first orchestration flow data, wherein the topology template datacomprises device template data representative of a node deviceassociated with the topology, and rules template data representative ofa connectivity rule associated with a service path topology.Additionally, the method can comprise in response to the applying thetopology template data to the first orchestration flow data, generating,by the wireless network device, second orchestration flow datarepresentative of a second service flow of the service of the wirelessnetwork.

According to another embodiment, a system can facilitate, receivingfirst orchestration flow data representative of a macro service flow ofa service of a wireless network. The system can also facilitate applyingtopology template data, representative of a topology, to the macroservice flow, wherein the topology template data comprises devicetemplate data representative of a node device associated with thetopology, and link template data representative of an endpointconnection. Furthermore, the system can comprise generating secondorchestration flow data representative of a micro service flow of theservice of the wireless network in response to the applying the topologytemplate data to the macro service flow.

According to yet another embodiment, described herein is amachine-readable storage medium that can perform the operationscomprising receiving first orchestration flow data representative of afirst service flow. The machine-readable storage medium can perform theoperations comprising applying a topology template associated with asecond service flow, to the first service flow, wherein the topologytemplate comprises rules template data representative of a connectivityrule associated with the second service flow, and link template datarepresentative of an endpoint connection within the topology template.Additionally, the machine-readable storage medium can perform theoperations comprising generating second orchestration flow datarepresentative of the second service flow in response to the applyingthe topology template to the first service flow.

These and other embodiments or implementations are described in moredetail below with reference to the drawings.

Referring now to FIG. 1 , illustrated is an example wirelesscommunication system 100 in accordance with various aspects andembodiments of the subject disclosure. In one or more embodiments,system 100 can comprise one or more user equipment UEs 102. Thenon-limiting term user equipment can refer to any type of device thatcan communicate with a network node in a cellular or mobilecommunication system. A UE can have one or more antenna panels havingvertical and horizontal elements. Examples of a UE comprise a targetdevice, device to device (D2D) UE, machine type UE or UE capable ofmachine to machine (M2M) communications, personal digital assistant(PDA), tablet, mobile terminals, smart phone, laptop mounted equipment(LME), universal serial bus (USB) dongles enabled for mobilecommunications, a computer having mobile capabilities, a mobile devicesuch as cellular phone, a laptop having laptop embedded equipment (LEE,such as a mobile broadband adapter), a tablet computer having a mobilebroadband adapter, a wearable device, a virtual reality (VR) device, aheads-up display (HUD) device, a smart car, a machine-type communication(MTC) device, and the like. User equipment UE 102 can also comprise IOTdevices that communicate wirelessly.

In various embodiments, system 100 is or comprises a wirelesscommunication network serviced by one or more wireless communicationnetwork providers. In example embodiments, a UE 102 can becommunicatively coupled to the wireless communication network via anetwork node 104. The network node (e.g., network node device) cancommunicate with user equipment (UE), thus providing connectivitybetween the UE and the wider cellular network. The UE 102 can sendtransmission type recommendation data to the network node 104. Thetransmission type recommendation data can comprise a recommendation totransmit data via a closed loop MIMO mode and/or a rank-1 precoder mode.

A network node can have a cabinet and other protected enclosures, anantenna mast, and multiple antennas for performing various transmissionoperations (e.g., MIMO operations). Network nodes can serve severalcells, also called sectors, depending on the configuration and type ofantenna. In example embodiments, the UE 102 can send and/or receivecommunication data via a wireless link to the network node 104. Thedashed arrow lines from the network node 104 to the UE 102 representdownlink (DL) communications and the solid arrow lines from the UE 102to the network nodes 104 represents an uplink (UL) communication.

System 100 can further include one or more communication serviceprovider networks 106 that facilitate providing wireless communicationservices to various UEs, including UE 102, via the network node 104and/or various additional network devices (not shown) included in theone or more communication service provider networks 106. The one or morecommunication service provider networks 106 can include various types ofdisparate networks, including but not limited to: cellular networks,femto networks, picocell networks, microcell networks, internet protocol(IP) networks Wi-Fi service networks, broadband service network,enterprise networks, cloud based networks, and the like. For example, inat least one implementation, system 100 can be or include a large scalewireless communication network that spans various geographic areas.According to this implementation, the one or more communication serviceprovider networks 106 can be or include the wireless communicationnetwork and/or various additional devices and components of the wirelesscommunication network (e.g., additional network devices and cell,additional UEs, network server devices, etc.). The network node 104 canbe connected to the one or more communication service provider networks106 via one or more backhaul links 108. For example, the one or morebackhaul links 108 can comprise wired link components, such as a T1/E1phone line, a digital subscriber line (DSL) (e.g., either synchronous orasynchronous), an asymmetric DSL (ADSL), an optical fiber backbone, acoaxial cable, and the like. The one or more backhaul links 108 can alsoinclude wireless link components, such as but not limited to,line-of-sight (LOS) or non-LOS links which can include terrestrialair-interfaces or deep space links (e.g., satellite communication linksfor navigation).

Wireless communication system 100 can employ various cellular systems,technologies, and modulation modes to facilitate wireless radiocommunications between devices (e.g., the UE 102 and the network node104). While example embodiments might be described for 5G new radio (NR)systems, the embodiments can be applicable to any radio accesstechnology (RAT) or multi-RAT system where the UE operates usingmultiple carriers e.g., LTE FDD/TDD, GSM/GERAN, CDMA2000 etc.

For example, system 100 can operate in accordance with global system formobile communications (GSM), universal mobile telecommunications service(UMTS), long term evolution (LTE), LTE frequency division duplexing (LTEFDD, LTE time division duplexing (TDD), high speed packet access (HSPA),code division multiple access (CDMA), wideband CDMA (WCMDA), CDMA2000,time division multiple access (TDMA), frequency division multiple access(FDMA), multi-carrier code division multiple access (MC-CDMA),single-carrier code division multiple access (SC-CDMA), single-carrierFDMA (SC-FDMA), orthogonal frequency division multiplexing (OFDM),discrete Fourier transform spread OFDM (DFT-spread OFDM) single carrierFDMA (SC-FDMA), Filter bank based multi-carrier (FBMC), zero tailDFT-spread-OFDM (ZT DFT-s-OFDM), generalized frequency divisionmultiplexing (GFDM), fixed mobile convergence (FMC), universal fixedmobile convergence (UFMC), unique word OFDM (UW-OFDM), unique wordDFT-spread OFDM (UW DFT-Spread-OFDM), cyclic prefix OFDM CP-OFDM,resource-block-filtered OFDM, Wi Fi, WLAN, WiMax, and the like. However,various features and functionalities of system 100 are particularlydescribed wherein the devices (e.g., the UEs 102 and the network device104) of system 100 are configured to communicate wireless signals usingone or more multi carrier modulation schemes, wherein data symbols canbe transmitted simultaneously over multiple frequency subcarriers (e.g.,OFDM, CP-OFDM, DFT-spread OFMD, UFMC, FMBC, etc.). The embodiments areapplicable to single carrier as well as to multicarrier (MC) or carrieraggregation (CA) operation of the UE. The term carrier aggregation (CA)is also called (e.g., interchangeably called) “multi-carrier system”,“multi-cell operation”, “multi-carrier operation”, “multi-carrier”transmission and/or reception. Note that some embodiments are alsoapplicable for Multi RAB (radio bearers) on some carriers (that is dataplus speech is simultaneously scheduled).

In various embodiments, system 100 can be configured to provide andemploy 5G wireless networking features and functionalities. 5G wirelesscommunication networks are expected to fulfill the demand ofexponentially increasing data traffic and to allow people and machinesto enjoy gigabit data rates with virtually zero latency. Compared to 4G,5G supports more diverse traffic scenarios. For example, in addition tothe various types of data communication between conventional UEs (e.g.,phones, smartphones, tablets, PCs, televisions, Internet enabledtelevisions, etc.) supported by 4G networks, 5G networks can be employedto support data communication between smart cars in association withdriverless car environments, as well as machine type communications(MTCs). Considering the drastic different communication needs of thesedifferent traffic scenarios, the ability to dynamically configurewaveform parameters based on traffic scenarios while retaining thebenefits of multi carrier modulation schemes (e.g., OFDM and relatedschemes) can provide a significant contribution to the highspeed/capacity and low latency demands of 5G networks. With waveformsthat split the bandwidth into several sub-bands, different types ofservices can be accommodated in different sub-bands with the mostsuitable waveform and numerology, leading to an improved spectrumutilization for 5G networks.

To meet the demand for data centric applications, features of proposed5G networks may comprise: increased peak bit rate (e.g., 20 Gbps),larger data volume per unit area (e.g., high system spectralefficiency—for example about 3.5 times that of spectral efficiency oflong term evolution (LTE) systems), high capacity that allows moredevice connectivity both concurrently and instantaneously, lowerbattery/power consumption (which reduces energy and consumption costs),better connectivity regardless of the geographic region in which a useris located, a larger numbers of devices, lower infrastructuraldevelopment costs, and higher reliability of the communications. Thus,5G networks may allow for: data rates of several tens of megabits persecond should be supported for tens of thousands of users, 1 gigabit persecond to be offered simultaneously to tens of workers on the sameoffice floor, for example; several hundreds of thousands of simultaneousconnections to be supported for massive sensor deployments; improvedcoverage, enhanced signaling efficiency; reduced latency compared toLTE.

The upcoming 5G access network may utilize higher frequencies (e.g., >6GHz) to aid in increasing capacity. Currently, much of the millimeterwave (mmWave) spectrum, the band of spectrum between 30 gigahertz (GHz)and 300 GHz is underutilized. The millimeter waves have shorterwavelengths that range from 10 millimeters to 1 millimeter, and thesemmWave signals experience severe path loss, penetration loss, andfading. However, the shorter wavelength at mmWave frequencies alsoallows more antennas to be packed in the same physical dimension, whichallows for large-scale spatial multiplexing and highly directionalbeamforming.

Performance can be improved if both the transmitter and the receiver areequipped with multiple antennas. Multi-antenna techniques cansignificantly increase the data rates and reliability of a wirelesscommunication system. The use of multiple input multiple output (MIMO)techniques, which was introduced in the third-generation partnershipproject (3GPP) and has been in use (including with LTE), is amulti-antenna technique that can improve the spectral efficiency oftransmissions, thereby significantly boosting the overall data carryingcapacity of wireless systems. The use of multiple-input multiple-output(MIMO) techniques can improve mmWave communications, and has been widelyrecognized a potentially important component for access networksoperating in higher frequencies. MIMO can be used for achievingdiversity gain, spatial multiplexing gain and beamforming gain. Forthese reasons, MIMO systems are an important part of the 3rd and 4thgeneration wireless systems, and are planned for use in 5G systems.

Referring now to FIG. 2 , illustrated is an example schematic systemblock diagram 200 of a service path design according to one or moreembodiments. A macro orchestration workflow can be a service providersystem that comprise work orders 206. The work orders for automated taskactivities can include, but are not limited to a request received date(RRD) auto inventory function, a path design final (PDF)) auto inventoryfunction, and/or an in-service date (ISD) auto status (e.g., active)change function. The GUI (e.g., mobile device 102) can use the RESTfulAPI 208, by utilizing an order microservices function 204, to inject acommand or the workflow. The RESTful API 208 can instantiate a servicetemplate, commit a service path design, and/or fetch the service path,within the microservices platform, by communicating with a topologytemplate 210. Thus, the GUI can utilize the RESTful API 208 to create aservice path and build it into an internal inventory database 224.

The topology template 210 can define the use cases for which the systemcan support by supporting a micro low to build links. To build a link,the microflow can determine if there is a port on a network device 104so that a link (e.g., jumper, fiber, segment, etc.) can be placed on theport. Then the system 200 can determine if resources on the other end ofthe link are available. Thereafter, sequencing can be used to placemultiple links together to create a path for a service for the networkdevice 104. Thus, the macroflow can inform the topology template 210 tobuild the microflow, wherein the microflow can also take into accountadditional data from various templates. The templates can comprise adevice template 212, a rule template 214, and/or a link template 216. Itshould be noted that in one or more embodiments, more or less templatescan be included within the system 200. The templates can also be storedin an internal database 224 and/or external database 232 connected tothe system via an abstraction layer 230. The abstraction layer cancommunicate with an inventory API/database driver 222, wherein theinventory API/database driver 222 can cache the network device 104 data(e.g., from the device template 212), service path from the inventory,and/or update the design into inventory. Any API call to themicroservice can then use any of the stored the designs. Data can alsobe cached and purged based on other system rules. Although the GUI canbe used to design and test the microservices, it should be noted that inother embodiments, the GUI 102 cannot be connected to the system.

The device template 212 comprises detailed mobile device 102 informationand can define a device (e.g., node 104 a, node 104 b, node 104 c) andits components with respect to a specific topology. For example, aspecific type of network device 104 can comprise slots, cards, ports,SFPs, Mux, DeMux, transponders, etc. The network device 104 type can becommunicated from the node 104 a, 104 b, 104 c to the device temple 212.This data can then be communicated to the topology template 210.

Rules 220 of the rules template 214 can be communicated to the topologytemplate 210. Rules can be associated with a backhaul, a common publicradio interface (CPRI)/fronthaul, and/or shorthaul. For instance, rulescan be used to allow a port on one network device 104 to be connected toanother port on another network device. Rules can be defined in terms ofhow to connect links (from the link template 216), cables, jumpers,fiber fidelity, wavelengths, etc. between network devices 104. Forexample, if there is a fiber connection, then a rule can mandate thatthe fiber connection be on the com port for the network device 104. Inanother example, if the system is transmitting a signal from networkdevice 104 A to network device 104C, via network device 104B, then arule can mandate that the signal be regenerated at network device 104Bfor transmission to network device 104 C. In yet another example, a rulecan mandate that a fiber connected to a specific port can regeneratesignals to pass data on specific wavelengths or switch wavelengths.Thus, in order to add add/drop a frequency of the wavelength, there canbe a transmission line and a reception line using redundant connectivityfor macro cell sites.

The link template 216 can comprise physical connections (e.g., fibers)and logical connections (e.g., wavelengths) and how the connections arerouted from point A to point Z. The link template 216 can determinewhich links are being supported. For example, to connect one DWDM device(e.g., network device 104) to another DWDM device, the fiber between thetwo can be connected. Sequencing can be used to build links and connectthose links to a physical fiber or channelize the fiber to a wavelength.In order to create an end-to-end connectivity, the fiber can beconnected to the DWDM devices, and then the fiber can be channelizedwith a specific wavelength. Channelizing the fiber comprises breakingdown a frequency from one point to another point. Noting that awavelength can change as it travels over different network segments, thesystem 200 can be designed to account for a decrease and/or increase infrequency by channelizing the fiber. Thus, based on whether thefrequency was decreased and/or increased, the wavelength can change sothat a path can be created to transmit data from one endpoint to anotherendpoint. The device template 212, rules template 214, and/or the linktemplate 216 can communicate their data to the topology template 210.The data received by the topology template 210, can then be used togenerate steps 226(a, b, c) of the microflow to generate a path topology228. It should be noted that one or more embodiments can contain some orall of the aforementioned templates.

Referring now to FIG. 3 , illustrated is an example schematic systemblock diagram of point-to-point service path 300 according to one ormore embodiments. As depicted in FIG. 3 , a network node 104 a can havea direct point-to-point connection to another network node 104 b via afiber pair 302, and/or the network node 1042 a can also have a diversefiber connection 304 for a lower frequency to network node 104 b.

Referring now to FIG. 4 , illustrated is an example schematic systemblock diagram of a hub service path 400 according to one or moreembodiments. The hub service path can have one network node 104 acommunicating with several network nodes 104 b, 104 c, 104 d (e.g.,spoke) over several links. For example, the network node 104 a cancommunicate with the network node 104 d over a different connection thanthe network node 104 a communicates with the network node 104 c. Itshould also be noted that as in FIG. 3 , the network node 1042 b canhave a fiber pair 302 and a diverse fiber connection 304 to the networknode 104 a. This should be considered a non-limiting embodiment in thatany number of the network nodes 104 b, 104 c, 104 d (e.g., spoke) can becapable of communicating with the mobile device 102 a over a fiber pairand/or a diverse fiber connection.

Referring now to FIG. 5 illustrates an example schematic system blockdiagram of a ring service path 500 according to one or more embodiments.The ring service path 500 can comprise remote network nodes 104 b, 104c, 104 d, 104 e, 104 f with a linear extension connection between thenetwork node 104 c and 104 g. The remote network nodes 104 b, 104 c, 104d, 104 e, 104 f can each have a linear connection between itself and itsneighboring mobile devices. For instance, the network node 104 c canhave a point-to-point connection with the network node 104 b and anotherpoint-to-point connection with the network node 104 d. The ring can beformed based on a connection beginning with the network node 104 a andanother connection ending with the network node 104 a, thus forming thering.

Referring now to FIG. 6 , illustrated is an example schematic systemblock diagram of combined service paths 600 according to one or moreembodiments. The depicted combined service paths 600 can comprise apoint-to-point service path as represented between the remote networknode 104 b, 104 c, 104 d, 104 e, 104 f, 104 g, 104 h, 104 i, 104 j, 104k. However, the remote mobile devices 104 b, 104 c, 104 d, 104 e, 104 f,104 g, 104 h, 104 i, 104 j, 104 k can form several rings around the hubmobile device 104 a. Thus, as opposed to the one ring depicted in FIG. 5, several rings are possible with respect to FIG. 6 .

Referring now to FIG. 7 , illustrated is an example schematic systemblock diagram of a ring routing option 700 according to one or moreembodiments. For example, a head/end network node 104 a can communicatewith a remote network node 104 b via a fiber pair connection after arule for the fiber is set. For example, a rule can tell the head/endnetwork node 104 a what port to connect the fiber to on the remotenetwork node 104 b. The A/D card from the head/end network node 104 acan connect to network node 104 b to provide connectivity to the macrocell site. Thus, the signal can be regenerated at the network node 104 bto pass wavelength data via a signal to the network node 104 c. In orderfor the add/drop at the network node 104 c there can be 2 lines at theSIAD to facilitate redundant connectivity for the cell site. Therefore,one line can be for transmissions and the other line can be forreception. The Mux/DeMux can be pluggable modules designed for acapacity needed for the links. Thus, the device template can have thedetails of the shelf, the cards, and the Mux that can be used tofacilitate the transmissions. The remote network node 104 b cancommunicate with another remote network node 104 c via another fiberpair connection. The remote network node 104 c can then communicate withthe hub network node 104 a via yet another fiber pair connection, thuscreating a ring service path.

Referring now to FIG. 8 , illustrated is an example flow diagram for amethod for a service path design network according to one or moreembodiments. At element 800 a method can comprise receiving (by a nodedevice 104) first orchestration flow data representative of a firstservice flow (e.g., work orders 206) of a service of a wireless network.At element 802, the method can also comprise applying (by a node device104) topology template data (from the topology template 210),representative of a topology, to the first orchestration flow data(e.g., work orders 206), wherein the topology template data comprisesdevice template data (from the device templates 212) representative of anode device 104 associated with the topology, and applying (by a nodedevice 104) rules template data (from the rules template 214)representative of a connectivity rule associated with a service pathtopology (e.g., path topology 22). Additionally, the method cancomprise, in response to the applying the topology template data (fromthe topology template 210) to the first orchestration flow data (e.g.,work orders 206), generating (by a node device 104) second orchestrationflow data representative of a second service flow (e.g., steps 226) ofthe service of the wireless network at element 804.

Referring now to FIG. 9 , illustrates an example flow diagram for asystem for a service path design network according to one or moreembodiments. A system can facilitate, receiving (by a node device 104)first orchestration flow data (e.g., work orders 206) representative ofa macro service flow of a service of a wireless network at element 900.At element 902, the system can also facilitate applying (by a nodedevice 104) topology template data (from topology templates 210),representative of a topology, to the macro service flow (e.g., workorders 206), wherein the topology template data comprises devicetemplate data (e.g., device templates 212) representative of a nodedevice 104 associated with the topology, and link template data (fromlink templates 216) representative of an endpoint connection.Furthermore, at element 904, the system can comprise generating (by thenode device 104) second orchestration flow data representative of amicro service flow (e.g., steps 226) of the service of the wirelessnetwork in response to the applying the topology template data to themacro service flow.

Referring now to FIG. 10 , illustrated is an example flow diagram for amachine-readable medium for a service path design network according toone or more embodiments. At element 1000 a machine-readable storagemedium can perform the operations comprising receiving (via the nodedevice 104) first orchestration flow data representative of a firstservice flow (e.g., work orders 206). At element 1002, themachine-readable storage medium can perform the operations comprisingapplying (via the network node device 104) a topology template (fromtopology templates 210) associated with a second service flow (e.g.,steps 226), to the first service flow (e.g., work orders 206), whereinthe topology template comprises rules template data (from the rulestemplate 214) representative of a connectivity rule associated with thesecond service flow (e.g., steps 226), and link template data (from linktemplates 216) representative of an endpoint connection within thetopology template 210. Additionally, at element 1004, themachine-readable storage medium can perform the operations comprisinggenerating (via the network node device 104) second orchestration flowdata representative of the second service flow (e.g., steps 226) inresponse to the applying the topology 210 template to the first serviceflow (e.g., work orders 206).

Referring now to FIG. 11 , illustrated is a schematic block diagram ofan exemplary end-user device such as a mobile device 1100 capable ofconnecting to a network in accordance with some embodiments describedherein. Although a mobile handset 1100 is illustrated herein, it will beunderstood that other devices can be a mobile device, and that themobile handset 1100 is merely illustrated to provide context for theembodiments of the various embodiments described herein. The followingdiscussion is intended to provide a brief, general description of anexample of a suitable environment 1100 in which the various embodimentscan be implemented. While the description includes a general context ofcomputer-executable instructions embodied on a machine-readable storagemedium, those skilled in the art will recognize that the innovation alsocan be implemented in combination with other program modules and/or as acombination of hardware and software.

Generally, applications (e.g., program modules) can include routines,programs, components, data structures, etc., that perform particulartasks or implement particular abstract data types. Moreover, thoseskilled in the art will appreciate that the methods described herein canbe practiced with other system configurations, includingsingle-processor or multiprocessor systems, minicomputers, mainframecomputers, as well as personal computers, hand-held computing devices,microprocessor-based or programmable consumer electronics, and the like,each of which can be operatively coupled to one or more associateddevices.

A computing device can typically include a variety of machine-readablemedia. Machine-readable media can be any available media that can beaccessed by the computer and includes both volatile and non-volatilemedia, removable and non-removable media. By way of example and notlimitation, computer-readable media can comprise computer storage mediaand communication media. Computer storage media can include volatileand/or non-volatile media, removable and/or non-removable mediaimplemented in any method or technology for storage of information, suchas computer-readable instructions, data structures, program modules orother data. Computer storage media can include, but is not limited to,RAM, ROM, EEPROM, flash memory or other memory technology, CD ROM,digital video disk (DVD) or other optical disk storage, magneticcassettes, magnetic tape, magnetic disk storage or other magneticstorage devices, or any other medium which can be used to store thedesired information and which can be accessed by the computer.

Communication media typically embodies computer-readable instructions,data structures, program modules or other data in a modulated datasignal such as a carrier wave or other transport mechanism, and includesany information delivery media. The term “modulated data signal” means asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in the signal. By way of example,and not limitation, communication media includes wired media such as awired network or direct-wired connection, and wireless media such asacoustic, RF, infrared and other wireless media. Combinations of the anyof the above should also be included within the scope ofcomputer-readable media.

The handset 1100 includes a processor 1102 for controlling andprocessing all onboard operations and functions. A memory 1104interfaces to the processor 1102 for storage of data and one or moreapplications 1106 (e.g., a video player software, user feedbackcomponent software, etc.). Other applications can include voicerecognition of predetermined voice commands that facilitate initiationof the user feedback signals. The applications 1106 can be stored in thememory 1104 and/or in a firmware 1108, and executed by the processor1102 from either or both the memory 1104 or/and the firmware 1108. Thefirmware 1108 can also store startup code for execution in initializingthe handset 1100. A communications component 1110 interfaces to theprocessor 1102 to facilitate wired/wireless communication with externalsystems, e.g., cellular networks, VoIP networks, and so on. Here, thecommunications component 1110 can also include a suitable cellulartransceiver 1111 (e.g., a GSM transceiver) and/or an unlicensedtransceiver 1113 (e.g., Wi-Fi, WiMax) for corresponding signalcommunications. The handset 1100 can be a device such as a cellulartelephone, a PDA with mobile communications capabilities, andmessaging-centric devices. The communications component 1110 alsofacilitates communications reception from terrestrial radio networks(e.g., broadcast), digital satellite radio networks, and Internet-basedradio services networks.

The handset 1100 includes a display 1112 for displaying text, images,video, telephony functions (e.g., a Caller ID function), setupfunctions, and for user input. For example, the display 1112 can also bereferred to as a “screen” that can accommodate the presentation ofmultimedia content (e.g., music metadata, messages, wallpaper, graphics,etc.). The display 1112 can also display videos and can facilitate thegeneration, editing and sharing of video quotes. A serial I/O interface1114 is provided in communication with the processor 1102 to facilitatewired and/or wireless serial communications (e.g., USB, and/or IEEE1394) through a hardwire connection, and other serial input devices(e.g., a keyboard, keypad, and mouse). This supports updating andtroubleshooting the handset 1100, for example. Audio capabilities areprovided with an audio I/O component 1116, which can include a speakerfor the output of audio signals related to, for example, indication thatthe user pressed the proper key or key combination to initiate the userfeedback signal. The audio I/O component 1116 also facilitates the inputof audio signals through a microphone to record data and/or telephonyvoice data, and for inputting voice signals for telephone conversations.

The handset 1100 can include a slot interface 1118 for accommodating aSIC (Subscriber Identity Component) in the form factor of a cardSubscriber Identity Module (SIM) or universal SIM 1120, and interfacingthe SIM card 1120 with the processor 1102. However, it is to beappreciated that the SIM card 1120 can be manufactured into the handset1100, and updated by downloading data and software.

The handset 1100 can process IP data traffic through the communicationcomponent 1110 to accommodate IP traffic from an IP network such as, forexample, the Internet, a corporate intranet, a home network, a personarea network, etc., through an ISP or broadband cable provider. Thus,VoIP traffic can be utilized by the handset 1100 and IP-based multimediacontent can be received in either an encoded or decoded format.

A video processing component 1122 (e.g., a camera) can be provided fordecoding encoded multimedia content. The video processing component 1122can aid in facilitating the generation, editing and sharing of videoquotes. The handset 1100 also includes a power source 1124 in the formof batteries and/or an AC power subsystem, which power source 1124 caninterface to an external power system or charging equipment (not shown)by a power I/O component 1126.

The handset 1100 can also include a video component 1130 for processingvideo content received and, for recording and transmitting videocontent. For example, the video component 1130 can facilitate thegeneration, editing and sharing of video quotes. A location trackingcomponent 1132 facilitates geographically locating the handset 1100. Asdescribed hereinabove, this can occur when the user initiates thefeedback signal automatically or manually. A user input component 1134facilitates the user initiating the quality feedback signal. The userinput component 1134 can also facilitate the generation, editing andsharing of video quotes. The user input component 1134 can include suchconventional input device technologies such as a keypad, keyboard,mouse, stylus pen, and/or touch screen, for example.

Referring again to the applications 1106, a hysteresis component 1136facilitates the analysis and processing of hysteresis data, which isutilized to determine when to associate with the access point. Asoftware trigger component 1138 can be provided that facilitatestriggering of the hysteresis component 1138 when the Wi-Fi transceiver1113 detects the beacon of the access point. A SIP client 1140 enablesthe handset 1100 to support SIP protocols and register the subscriberwith the SIP registrar server. The applications 1106 can also include aclient 1142 that provides at least the capability of discovery, play andstore of multimedia content, for example, music.

The handset 1100, as indicated above related to the communicationscomponent 810, includes an indoor network radio transceiver 1113 (e.g.,Wi-Fi transceiver). This function supports the indoor radio link, suchas IEEE 802.11, for the dual-mode GSM handset 1100. The handset 1100 canaccommodate at least satellite radio services through a handset that cancombine wireless voice and digital radio chipsets into a single handhelddevice.

Referring now to FIG. 12 , there is illustrated a block diagram of acomputer 1200 operable to execute a system architecture that facilitatesestablishing a transaction between an entity and a third party. Thecomputer 1200 can provide networking and communication capabilitiesbetween a wired or wireless communication network and a server (e.g.,Microsoft server) and/or communication device. In order to provideadditional context for various aspects thereof, FIG. 12 and thefollowing discussion are intended to provide a brief, generaldescription of a suitable computing environment in which the variousaspects of the innovation can be implemented to facilitate theestablishment of a transaction between an entity and a third party.While the description above is in the general context ofcomputer-executable instructions that can run on one or more computers,those skilled in the art will recognize that the innovation also can beimplemented in combination with other program modules and/or as acombination of hardware and software.

Generally, program modules include routines, programs, components, datastructures, etc., that perform particular tasks or implement particularabstract data types. Moreover, those skilled in the art will appreciatethat the various methods can be practiced with other computer systemconfigurations, including single-processor or multiprocessor computersystems, minicomputers, mainframe computers, as well as personalcomputers, hand-held computing devices, microprocessor-based orprogrammable consumer electronics, and the like, each of which can beoperatively coupled to one or more associated devices.

The illustrated aspects of the innovation can also be practiced indistributed computing environments where certain tasks are performed byremote processing devices that are linked through a communicationsnetwork. In a distributed computing environment, program modules can belocated in both local and remote memory storage devices.

Computing devices typically include a variety of media, which caninclude computer-readable storage media or communications media, whichtwo terms are used herein differently from one another as follows.

Computer-readable storage media can be any available storage media thatcan be accessed by the computer and includes both volatile andnonvolatile media, removable and non-removable media. By way of example,and not limitation, computer-readable storage media can be implementedin connection with any method or technology for storage of informationsuch as computer-readable instructions, program modules, structureddata, or unstructured data. Computer-readable storage media can include,but are not limited to, RAM, ROM, EEPROM, flash memory or other memorytechnology, CD-ROM, digital versatile disk (DVD) or other optical diskstorage, magnetic cassettes, magnetic tape, magnetic disk storage orother magnetic storage devices, or other tangible and/or non-transitorymedia which can be used to store desired information. Computer-readablestorage media can be accessed by one or more local or remote computingdevices, e.g., via access requests, queries or other data retrievalprotocols, for a variety of operations with respect to the informationstored by the medium.

Communications media can embody computer-readable instructions, datastructures, program modules or other structured or unstructured data ina data signal such as a modulated data signal, e.g., a carrier wave orother transport mechanism, and includes any information delivery ortransport media. The term “modulated data signal” or signals refers to asignal that has one or more of its characteristics set or changed insuch a manner as to encode information in one or more signals. By way ofexample, and not limitation, communication media include wired media,such as a wired network or direct-wired connection, and wireless mediasuch as acoustic, RF, infrared and other wireless media.

With reference to FIG. 12 , implementing various aspects describedherein with regards to the end-user device can include a computer 1200,the computer 1200 including a processing unit 1204, a system memory 1206and a system bus 1208. The system bus 1208 couples system componentsincluding, but not limited to, the system memory 1206 to the processingunit 1204. The processing unit 1204 can be any of various commerciallyavailable processors. Dual microprocessors and other multi processorarchitectures can also be employed as the processing unit 1204.

The system bus 1208 can be any of several types of bus structure thatcan further interconnect to a memory bus (with or without a memorycontroller), a peripheral bus, and a local bus using any of a variety ofcommercially available bus architectures. The system memory 1206includes read-only memory (ROM) 1227 and random access memory (RAM)1212. A basic input/output system (BIOS) is stored in a non-volatilememory 1227 such as ROM, EPROM, EEPROM, which BIOS contains the basicroutines that help to transfer information between elements within thecomputer 1200, such as during start-up. The RAM 1212 can also include ahigh-speed RAM such as static RAM for caching data.

The computer 1200 further includes an internal hard disk drive (HDD)1214 (e.g., EIDE, SATA), which internal hard disk drive 1214 can also beconfigured for external use in a suitable chassis (not shown), amagnetic floppy disk drive (FDD) 1216, (e.g., to read from or write to aremovable diskette 1218) and an optical disk drive 1220, (e.g., readinga CD-ROM disk 1222 or, to read from or write to other high capacityoptical media such as the DVD). The hard disk drive 1214, magnetic diskdrive 1216 and optical disk drive 1220 can be connected to the systembus 1208 by a hard disk drive interface 1224, a magnetic disk driveinterface 1226 and an optical drive interface 1228, respectively. Theinterface 1224 for external drive implementations includes at least oneor both of Universal Serial Bus (USB) and IEEE 1294 interfacetechnologies. Other external drive connection technologies are withincontemplation of the subject innovation.

The drives and their associated computer-readable media providenonvolatile storage of data, data structures, computer-executableinstructions, and so forth. For the computer 1200 the drives and mediaaccommodate the storage of any data in a suitable digital format.Although the description of computer-readable media above refers to aHDD, a removable magnetic diskette, and a removable optical media suchas a CD or DVD, it should be appreciated by those skilled in the artthat other types of media which are readable by a computer 1200, such aszip drives, magnetic cassettes, flash memory cards, cartridges, and thelike, can also be used in the exemplary operating environment, andfurther, that any such media can contain computer-executableinstructions for performing the methods of the disclosed innovation.

A number of program modules can be stored in the drives and RAM 1212,including an operating system 1230, one or more application programs1232, other program modules 1234 and program data 1236. All or portionsof the operating system, applications, modules, and/or data can also becached in the RAM 1212. It is to be appreciated that the innovation canbe implemented with various commercially available operating systems orcombinations of operating systems.

A user can enter commands and information into the computer 1200 throughone or more wired/wireless input devices, e.g., a keyboard 1238 and apointing device, such as a mouse 1240. Other input devices (not shown)may include a microphone, an IR remote control, a joystick, a game pad,a stylus pen, touch screen, or the like. These and other input devicesare often connected to the processing unit 1204 through an input deviceinterface 1242 that is coupled to the system bus 1208, but can beconnected by other interfaces, such as a parallel port, an IEEE 2394serial port, a game port, a USB port, an IR interface, etc.

A monitor 1244 or other type of display device is also connected to thesystem bus 1208 through an interface, such as a video adapter 1246. Inaddition to the monitor 1244, a computer 1200 typically includes otherperipheral output devices (not shown), such as speakers, printers, etc.

The computer 1200 can operate in a networked environment using logicalconnections by wired and/or wireless communications to one or moreremote computers, such as a remote computer(s) 1248. The remotecomputer(s) 1248 can be a workstation, a server computer, a router, apersonal computer, portable computer, microprocessor-based entertainmentdevice, a peer device or other common network node, and typicallyincludes many or all of the elements described relative to the computer,although, for purposes of brevity, only a memory/storage device 1250 isillustrated. The logical connections depicted include wired/wirelessconnectivity to a local area network (LAN) 1252 and/or larger networks,e.g., a wide area network (WAN) 1254. Such LAN and WAN networkingenvironments are commonplace in offices and companies, and facilitateenterprise-wide computer networks, such as intranets, all of which mayconnect to a global communications network, e.g., the Internet.

When used in a LAN networking environment, the computer 1200 isconnected to the local network 1252 through a wired and/or wirelesscommunication network interface or adapter 1256. The adapter 1256 mayfacilitate wired or wireless communication to the LAN 1252, which mayalso include a wireless access point disposed thereon for communicatingwith the wireless adapter 1256.

When used in a WAN networking environment, the computer 1200 can includea modem 1258, or is connected to a communications server on the WAN1254, or has other means for establishing communications over the WAN1254, such as by way of the Internet. The modem 1258, which can beinternal or external and a wired or wireless device, is connected to thesystem bus 1208 through the input device interface 1242. In a networkedenvironment, program modules depicted relative to the computer, orportions thereof, can be stored in the remote memory/storage device1250. It will be appreciated that the network connections shown areexemplary and other means of establishing a communications link betweenthe computers can be used.

The computer is operable to communicate with any wireless devices orentities operatively disposed in wireless communication, e.g., aprinter, scanner, desktop and/or portable computer, portable dataassistant, communications satellite, any piece of equipment or locationassociated with a wirelessly detectable tag (e.g., a kiosk, news stand,restroom), and telephone. This includes at least Wi-Fi and Bluetooth™wireless technologies. Thus, the communication can be a predefinedstructure as with a conventional network or simply an ad hoccommunication between at least two devices.

Wi-Fi, or Wireless Fidelity, allows connection to the Internet from acouch at home, a bed in a hotel room, or a conference room at work,without wires. Wi-Fi is a wireless technology similar to that used in acell phone that enables such devices, e.g., computers, to send andreceive data indoors and out; anywhere within the range of a basestation. Wi-Fi networks use radio technologies called IEEE 802.11 (a, b,g, etc.) to provide secure, reliable, fast wireless connectivity. AWi-Fi network can be used to connect computers to each other, to theInternet, and to wired networks (which use IEEE 802.3 or Ethernet).Wi-Fi networks operate in the unlicensed 2.4 and 5 GHz radio bands, atan 11 Mbps (802.11a) or 54 Mbps (802.11b) data rate, for example, orwith products that contain both bands (dual band), so the networks canprovide real-world performance similar to the basic 10BaseT wiredEthernet networks used in many offices.

Mobile transport connectivity design (e.g., switched Ethernet, dedicatedEthernet, DWDM, etc.), is a major challenge for automation of servicepath design that can have significant cost investment and long leadtimes to develop automation within monolithic network managementapplications. Support for various use cases and continuous changeswithin a monolithic network management can be costly and requireadvanced planning. There are currently no available containerizedcloud-based micro service tools that can provide a meta-data drivenapproach for automation of service path design with flexibility tosupport various DWDM use cases and add new use cases by meta-data.

The above description of illustrated embodiments of the subjectdisclosure, including what is described in the Abstract, is not intendedto be exhaustive or to limit the disclosed embodiments to the preciseforms disclosed. While specific embodiments and examples are describedherein for illustrative purposes, various modifications are possiblethat are considered within the scope of such embodiments and examples,as those skilled in the relevant art can recognize.

In this regard, while the subject matter has been described herein inconnection with various embodiments and corresponding FIGs, whereapplicable, it is to be understood that other similar embodiments can beused or modifications and additions can be made to the describedembodiments for performing the same, similar, alternative, or substitutefunction of the disclosed subject matter without deviating therefrom.Therefore, the disclosed subject matter should not be limited to anysingle embodiment described herein, but rather should be construed inbreadth and scope in accordance with the appended claims below.

What is claimed is:
 1. A method, comprising: applying, by a systemcomprising a processor, a network topology template to macroorchestration flow data associated with a network service, wherein thenetwork topology template is representative of a network topologyapplicable to the network service, and wherein the network topologytemplate comprises device data, representative of respective nodedevices associated with the network topology, and link data,representative of connection endpoints associated with the respectivenode devices; and generating, by the system in response to the applying,micro orchestration flow data representative of a service path, for amicroservice to be associated with the network service, within thenetwork topology.
 2. The method of claim 1, further comprising:receiving, by the system, a request for the micro orchestration flowdata, wherein the applying is in response to the receiving of therequest.
 3. The method of claim 1, further comprising: sending, by thesystem, the micro orchestration flow data to the network service; andreceiving, by the system in response to the sending of the microorchestration flow data, a request to instantiate the microservice. 4.The method of claim 3, further comprising: instantiating, by the systemin response to the receiving of the request, the microservice.
 5. Themethod of claim 1, wherein the network topology template furthercomprises rules data representative of a rule that defines connectivitybetween the respective node devices.
 6. The method of claim 1, whereinthe connection endpoints associated with the respective node devices areoptical connection endpoints.
 7. The method of claim 1, furthercomprising: retrieving, by the system, the device data from a datastore.
 8. The method of claim 1, further comprising: storing, by thesystem in response to the generating of the micro orchestration flowdata, service path data, representative of the service path, to a datastore.
 9. The method of claim 8, wherein the service path is a firstservice path, wherein the service path data is first service path data,wherein the network service is a first network service, wherein thegenerating of the micro orchestration flow data is based on secondservice path data stored in the data store, and wherein the secondservice path data is representative of a second service path associatedwith a second network service.
 10. A system, comprising: a processor;and a memory that stores executable instructions that, when executed bythe processor, facilitate performance of operations, comprising:applying topology template data to a macro orchestration flow associatedwith a network service, wherein the topology template data isrepresentative of a network topology applicable to the network service,and wherein the topology template data comprises device template data,representative of respective node devices within the network topology,and link template data, representative of connection endpoints betweenthe respective node devices; and generating, in response to theapplying, a micro orchestration flow representative of a service path,for a microservice to be associated with the network service, within thenetwork topology.
 11. The system of claim 10, wherein the operationsfurther comprise: receiving a request for the micro orchestration flow,wherein the applying is in response to the receiving of the request. 12.The system of claim 10, wherein the operations further comprise:conveying the micro orchestration flow to the network service; inresponse to the conveying, receiving a request to instantiate themicroservice; and in response to the receiving of the request,instantiating the microservice.
 13. The system of claim 10, wherein thetopology template data further comprises rules template datarepresentative of a rule that defines connectivity between therespective node devices.
 14. The system of claim 10, wherein theoperations further comprise: in response to the generating of the microorchestration flow, storing service path data, representative of theservice path, to a database.
 15. The system of claim 14, wherein theservice path is a first service path, wherein the service path data isfirst service path data, wherein the network service is a first networkservice, and wherein the generating of the micro orchestration flow isbased on second service path data stored in the database, the secondservice path data being representative of a second service pathassociated with a second network service.
 16. A non-transitorymachine-readable medium, comprising executable instructions that, whenexecuted by a processor, facilitate performance of operations,comprising: applying topology template data, representative of atopology of a communication network, to first orchestration flow dataassociated with a network service, the topology template data comprisingdevice data, representative of network devices associated with thecommunication network, and link data, representative of connectionendpoints associated with the network devices; and generating, inresponse to the applying, second orchestration flow data, the secondorchestration flow data being representative of a service path, withinthe topology of the communication network, wherein the secondorchestration flow data is applicable to a microservice to be associatedwith the network service.
 17. The non-transitory machine-readable mediumof claim 16, wherein the operations further comprise: receiving arequest for the first orchestration flow data via the network service,wherein the applying is in response to the receiving of the request. 18.The non-transitory machine-readable medium of claim 16, wherein theoperations further comprise: communicating the second orchestration flowdata to the network service; in response to the communicating of thesecond orchestration flow data, receiving a request to instantiate themicroservice via the network service; and in response to the receivingof the request, instantiating the microservice.
 19. The non-transitorymachine-readable medium of claim 16, wherein the topology template datafurther comprises rules data representative of a rule that definesconnectivity between the network devices.
 20. The non-transitorymachine-readable medium of claim 16, wherein the service path is a firstservice path, wherein the network service is a first network service,and wherein the generating of the second orchestration flow data isbased on stored service path data, the stored service path data beingrepresentative of a second service path associated with a second networkservice.